Jira (PUP-10111) Update Public-facing Puppet docs to include OSX Catalina 10.15 (amd64)
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10111 Update Public-facing Puppet docs to include OSX Catalina 10.15 (amd64) Change By: Mihai Buzgau Sprint: NW - 2020-02-05 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.331949.1571920219000.31582.1579679880175%40Atlassian.JIRA.
Jira (PUP-10111) Update Public-facing Puppet docs to include OSX Catalina 10.15 (amd64)
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10111 Update Public-facing Puppet docs to include OSX Catalina 10.15 (amd64) Change By: Mihai Buzgau Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.331949.1571920219000.31581.1579679880121%40Atlassian.JIRA.
Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Gheorghe Popescu commented on FACT-1858 Re: Provide an option to disable legacy facts so they are not sent to the master from the agent We can have a ticket for that but we can do the changes only when Facter 2.x is no longer used in puppet gem(it only knows legacy facts). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.253867.1527713421000.31571.1579679640387%40Atlassian.JIRA.
Jira (PUP-10247) Support ruby 2.7
Title: Message Title Josh Cooper created an issue Puppet / PUP-10247 Support ruby 2.7 Issue Type: Task Assignee: Unassigned Created: 2020/01/21 10:47 PM Priority: Normal Reporter: Josh Cooper puppet specs fail on ruby 2.7.0 because: sync was extracted into a different gem. But we don't actually need that code, so remove the require 'sync' statements. scanf was extracted into a different gem. We need to add a runtime dependency on that gem ~> 1.0 to puppet's .gemspec. We will need to update a few other projects first (puppetserver, r10k, etc) first. There many ruby deprecation warnings due to keyword argument vs positional argument handling. See https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/ Add Comment
Jira (PDOC-273) puppet-strings should pull documentation from the lib folder too
Title: Message Title Josh Cooper updated an issue Puppet Strings / PDOC-273 puppet-strings should pull documentation from the lib folder too Change By: Josh Cooper Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.294635.1549292365000.31562.1579674720223%40Atlassian.JIRA.
Jira (PUP-10240) Puppet gem has no/missing development/test gems
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10240 Puppet gem has no/missing development/test gems Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342644.1579458924000.31558.1579674480116%40Atlassian.JIRA.
Jira (PUP-10240) Puppet gem has no/missing development/test gems
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10240 Puppet gem has no/missing development/test gems Change By: Josh Cooper Fix Version/s: PUP 6.13.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342644.1579458924000.31555.1579674420339%40Atlassian.JIRA.
Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Josh Cooper commented on FACT-1858 Re: Provide an option to disable legacy facts so they are not sent to the master from the agent Should there be another ticket for finding those places in Puppet that use legacy fact names and updating them to use structured fact names? We should at least be internally consistent. Please file a PUP ticket. Will *_core modules also need to change? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.253867.1527713421000.31531.1579672560533%40Atlassian.JIRA.
Jira (PUP-10234) Add ppAuthCertExt to custom_extensions
Title: Message Title
Josh Cooper commented on PUP-10234
Re: Add ppAuthCertExt to custom_extensions
Puppet is correctly embedding the certificate extension and will return it provided the oids have been registered:
[root@ornate-micelle ~]# /opt/puppetlabs/puppet/bin/irb
irb(main):001:0> require 'puppet'
=> true
irb(main):002:0> Puppet.initialize_settings
=> [:debug, :info, :notice, :warning, :err, :alert, :emerg, :crit]
irb(main):003:0> x509 = Puppet::SSL::Certificate.from_s(File.read('/etc/puppetlabs/puppet/ssl/certs/ornate-micelle.delivery.puppetlabs.net.pem'))
=> #, issuer=#, serial=#, not_before=2020-01-21 01:43:17 UTC, not_after=2025-01-20 01:43:17 UTC>>
irb(main):004:0> x509.custom_extensions
=> []
irb(main):005:0> Puppet::SSL::Oids.register_puppet_oids
=> true
irb(main):006:0> x509.custom_extensions
Jira (PUP-10173) Set CI jobs to run only 'high' risk acceptance tests
Title: Message Title Melissa Stone commented on PUP-10173 Re: Set CI jobs to run only 'high' risk acceptance tests I want to keep this open for a day or two to make sure we get a good run of puppet and friends Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.339228.1576177064000.31450.1579654440240%40Atlassian.JIRA.
Jira (PUP-10173) Set CI jobs to run only 'high' risk acceptance tests
Title: Message Title Melissa Stone updated an issue Puppet / PUP-10173 Set CI jobs to run only 'high' risk acceptance tests Change By: Melissa Stone Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.339228.1576177064000.31444.1579654380204%40Atlassian.JIRA.
Jira (PUP-10173) Set CI jobs to run only 'high' risk acceptance tests
Title: Message Title Melissa Stone commented on PUP-10173 Re: Set CI jobs to run only 'high' risk acceptance tests Merged into the master branch of ci-job-configs at https://github.com/puppetlabs/ci-job-configs/commit/a0f9eca968653fcb45ed470116ab02077a6f11bf Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.339228.1576177064000.31441.1579654320351%40Atlassian.JIRA.
Jira (PUP-9563) Using max_queued_requests, agents return to originally scheduled run times
Title: Message Title Josh Cooper commented on PUP-9563 Re: Using max_queued_requests, agents return to originally scheduled run times I'm not against this idea, but it'd be good to consider the impact on: How does this work when puppet run out of cron? I think some there are some other platforms like AIX that behave like Windows where the start time is set by an external process. Also splay on Windows doesn't behave like nix, see PUP-5823. What happens if the Retry-After times causes the agent to exceed its runinterval? What if the agent hits multiple Retry-After's, such as during pluginsync? What happens if the server is temporarily down (eg due to puppetserver reload) and now agents are re-splayed until the puppet service restarts? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.299686.1552405921000.31163.1579647060420%40Atlassian.JIRA.
Jira (PUP-10142) Make Puppet settings not change after a request is initiated
Title: Message Title Maggie Dreyer assigned an issue to Tony Vu Puppet / PUP-10142 Make Puppet settings not change after a request is initiated Change By: Maggie Dreyer Assignee: Justin Stoller Tony Vu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323044.1567197022000.31116.1579646400527%40Atlassian.JIRA.
Jira (PUP-10240) Puppet gem has no/missing development/test gems
Title: Message Title Tim Meusel commented on PUP-10240 Re: Puppet gem has no/missing development/test gems Hi Jorie Tappa! I'm building the official Arch Linux packages for Puppet tools. That includes r10k, pdk and Puppet. The abstract workflow for Arch packages looks like this: Setup a minimal Arch container Download the release. e.g. a git tag or a tar ball from http://downloads.puppet.com/ Install all dependencies required to run tests + to built it via native Arch packages Run the tests "build" the software specific for Puppet: At the moment we download the release from https://downloads.puppetlabs.com/, verify the signature and try to install required dependencies. Since puppet is published as a gem, I went the usual way for gems -> checking required depdencies on rubygems.org / in the gemspec file. Most projects I work with define runtime + test dependencies in the gemspec. Stuff that's nice for development is defined in a Gemfile. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-9750) optionally add pe_version to server_facts
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9750
optionally add pe_version to server_facts
Change By:
Josh Cooper
Members of the Puppet Community have requested a standardized best practice to determine if a Puppet Agent is a PE or FOSS Puppet Agent. Since Puppet 4.x, there is no concept of a PE or FOSS Puppet Agent, but a Puppet Agent can be served a catalog by a PE or FOSS Puppet Server.A non-empty {{pe_version}} fact would both differentiate between PE or FOSS, but would allow for conditional code depending upon the specific version of PE.The {{pe_version}} fact is available in Puppet / PE 3.x.The {{pe_compiling_server_version}} function (which calls {{pe_server_version}}) is available on a PE Puppet Server after PE 3.x, but is not available on a FOSS Puppet Server, requiring the use of the {{is_function_available} } function to avoid generating an error when calling {{pe_compiling_server_version}} function on a FOSS Puppet Server.The {{is_function_available}} function is itself now deprecated.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10239) Modules should have the ability to add data to the Hiera layer of the module and have it affect other modules default lookup settings.
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-10239 Modules should have the ability to add data to the Hiera layer of the module and have it affect other modules default lookup settings. Change By: Jorie Tappa Team: Froyo Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342592.1579287213000.31027.1579643220567%40Atlassian.JIRA.
Jira (PUP-10239) Modules should have the ability to add data to the Hiera layer of the module and have it affect other modules default lookup settings.
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-10239 Modules should have the ability to add data to the Hiera layer of the module and have it affect other modules default lookup settings. Change By: Jorie Tappa Sub-team: Language Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342592.1579287213000.31030.1579643220699%40Atlassian.JIRA.
Jira (PUP-10240) Puppet gem has no/missing development/test gems
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-10240 Puppet gem has no/missing development/test gems Change By: Jorie Tappa Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342644.1579458924000.31021.1579643160135%40Atlassian.JIRA.
Jira (PUP-10240) Puppet gem has no/missing development/test gems
Title: Message Title Jorie Tappa commented on PUP-10240 Re: Puppet gem has no/missing development/test gems Hi Tim Meusel you can view our development and test gem groups directly in our Puppet repo, if that's helpful here: https://github.com/puppetlabs/puppet/blob/master/Gemfile#L38-L58 What workflow are you using that would make having them in the puppet gem itself easier for you? Right now we don't have a good way to include these items there. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342644.1579458924000.31018.1579642980105%40Atlassian.JIRA.
Jira (PDB-4630) Merge-up, branch, and create pipelines (PuppetDB 6.8.1)
Title: Message Title
Austin Blatt created an issue
PuppetDB / PDB-4630
Merge-up, branch, and create pipelines (PuppetDB 6.8.1)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2020/01/21 10:29 AM
Due Date:
2020/01/15
Priority:
Normal
Reporter:
Austin Blatt
(Initial planned release date: 2020-01-22) Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS).
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
5.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Merge 5.2.x -> 6.3.x
Merge 6.3.x ->
Jira (PDB-4631) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.8.1)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4631 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.8.1) Issue Type: Task Assignee: Austin Blatt Created: 2020/01/21 10:29 AM Due Date: 2020/01/15 Priority: Normal Reporter: Austin Blatt (Initial planned release date: 2020-01-22) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Once fixVersions are set for all tickets, verify that each ticket has the proper release notes Add Comment
Jira (PDB-4632) Bump versions, push directly, and tag (PuppetDB 6.8.1)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4632 Bump versions, push directly, and tag (PuppetDB 6.8.1) Issue Type: Task Assignee: Austin Blatt Created: 2020/01/21 10:29 AM Due Date: 2020/01/18 Priority: Normal Reporter: Austin Blatt (Initial planned release date: 2020-01-22) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Disable automatic promotions: If this release will be released in a PE release, disable automatic promotions on the branch(es) you are releasing from. This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example. Set the real version for release: Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing. Go into the '#release-new-new' Slack channel to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in the
Jira (PDB-4633) Check builds, promote to PE (PuppetDB 6.8.1)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4633 Check builds, promote to PE (PuppetDB 6.8.1) Issue Type: Task Assignee: Austin Blatt Created: 2020/01/21 10:29 AM Due Date: 2020/01/18 Priority: Normal Reporter: Austin Blatt (Initial planned release date: 2020-01-22) Check that all the builds are green. Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PDB-4629) PuppetDB 6.8.1 2020-01-22 Release
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4629 PuppetDB 6.8.1 2020-01-22 Release Issue Type: Epic Assignee: Austin Blatt Created: 2020/01/21 10:29 AM Priority: Normal Reporter: Austin Blatt PuppetDB 6.8.1 2020-01-22 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4634) Update winston (PuppetDB 6.8.1)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4634 Update winston (PuppetDB 6.8.1) Issue Type: Task Assignee: Austin Blatt Created: 2020/01/21 10:29 AM Due Date: 2020/01/23 Priority: Normal Reporter: Austin Blatt (Initial planned release date: 2020-01-22) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9213) Puppet agent should indicate which HTTP timeout has expired
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9213 Puppet agent should indicate which HTTP timeout has expired Change By: Josh Cooper Sprint: Coremunity Grooming Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.279317.1539016372000.30481.1579628760531%40Atlassian.JIRA.
Jira (PUP-10226) URL encode paths in http client
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10226 URL encode paths in http client Change By: Josh Cooper Sprint: Coremunity Grooming Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341489.1578519209000.30476.1579628760311%40Atlassian.JIRA.
Jira (PUP-10227) Close the http connection prior to sleeping retry-after seconds
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10227 Close the http connection prior to sleeping retry-after seconds Change By: Josh Cooper Sprint: Coremunity Grooming Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341492.1578520569000.30475.1579628760267%40Atlassian.JIRA.
Jira (PUP-10018) The module tool won't solve some dependencies without --force or --ignore-dependencies
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10018 The module tool won't solve some dependencies without --force or --ignore-dependencies Change By: Josh Cooper Sprint: Coremunity Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324663.1568391367000.30474.1579628700225%40Atlassian.JIRA.
Jira (PUP-10142) Make Puppet settings not change after a request is initiated
Title: Message Title Maggie Dreyer commented on PUP-10142 Re: Make Puppet settings not change after a request is initiated This is currently waiting on further hashing out of the right approach, see comments on https://github.com/puppetlabs/puppet/pull/7746 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323044.1567197022000.30450.1579627560288%40Atlassian.JIRA.
Jira (PUP-10234) Add ppAuthCertExt to custom_extensions
Title: Message Title Christopher Thorn updated an issue Puppet / PUP-10234 Add ppAuthCertExt to custom_extensions Change By: Christopher Thorn Attachment: genteel-drift.delivery.puppetlabs.net.pem Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342045.1579029203000.30431.1579627440964%40Atlassian.JIRA.
Jira (PUP-10236) Audit and tag untagged puppet acceptance tests
Title: Message Title Josh Cooper commented on PUP-10236 Re: Audit and tag untagged puppet acceptance tests Passed master in d90862369 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342254.1579118245000.30435.1579627441139%40Atlassian.JIRA.
Jira (FACT-2306) Add support for AWS IMDSv2
Title: Message Title Bryan Woolsey updated an issue Facter / FACT-2306 Add support for AWS IMDSv2 Change By: Bryan Woolsey Amazon recently released version 2 of their instance metadata service. The new service is session-oriented rather than a simple request/response HTTP call, and was created in response to recent security breaches.Facter currently only seems to support version 1 of the metadata service for the ec2_metadata and ec2_userdata facts , making it difficult for Puppet users in high-security environments to transition to version 2 of the service.[https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html] Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (FACT-2306) Add support for AWS IMDSv2
Title: Message Title Bryan Woolsey updated an issue Facter / FACT-2306 Add support for AWS IMDSv2 Change By: Bryan Woolsey Amazon recently released version 2 of their instance metadata service. The new service is session-oriented rather than a simple request/response HTTP call, and was created in response to recent security breaches.Facter currently only seems to support version 1 of the metadata service, making it difficult for Puppet users in high-security environments to transition to version 2 of the service.[https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html] Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (FACT-2306) Add support for AWS IMDSv2
Title: Message Title Bryan Woolsey created an issue Facter / FACT-2306 Add support for AWS IMDSv2 Issue Type: New Feature Assignee: Unassigned Created: 2020/01/21 9:13 AM Priority: Normal Reporter: Bryan Woolsey Amazon recently released version 2 of their instance metadata service. The new service is session-oriented rather than a simple request/response HTTP call, and was created in response to recent security breaches. Facter currently only seems to support version 1 of the metadata service, making it difficult for Puppet users to transition to version 2 of the service. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html Add Comment This message was
Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Nick Walker commented on FACT-1858 Re: Provide an option to disable legacy facts so they are not sent to the master from the agent created PDK-1591 for PDK support of this option. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.253867.1527713421000.30288.1579624381935%40Atlassian.JIRA.
Jira (PDB-4626) Investigate resource_events partitioning migration failure
Title: Message Title
Michael Prokop commented on PDB-4626
Re: Investigate resource_events partitioning migration failure
FTR, a customer of mine is also affected by this: mika@puppet ~ % sudo zless /var/log/puppetlabs/puppetdb/puppetdb-2020-01-15.0.log.gz[...]2020-01-15T06:55:45.426+01:00 ERROR [p.p.s.migrate] Caught SQLException during migration java.sql.BatchUpdateException: Batch entry 0 INSERT INTO resource_events_20200103Z ( event_hash, report_id, certname_id, status, timestamp, resource_type, resource_title, property, new_value, old_value, message, file, line, containment_path, containing_class, corrective_change, name ) VALUES ( '\x501aa8aa6d7d2a66d7b93ca07a8fbe63e36c8d77', 429028, 14, 'skipped', '2020-01-03 06:58:06.805+01', 'Exec', '/usr/bin/gitlab-ctl reconfigure', NULL, 'null', 'null', NULL, '/etc/puppetlabs/code/environments/production/site/gitlab/manifests/server.pp', 13, '{Stage[main],Gitlab::Server,"Exec[/usr/bin/gitlab-ctl reconfigure]"}', 'Gitlab::Server', NULL, NULL ),( '\x403832e909d515158843a61847ea20ae92468e1a', 429028, 14, 'skipped', '2020-01-03 06:58:06.801+01', 'File', '/etc/gitlab/gitlab.rb', NULL, 'null', 'null', NULL, '/etc/puppetlabs/code/environments/production/site/gitlab/manifests/server.pp', 7, '{Stage[main],Gitlab::Server,File[/etc/gitlab/gitlab.rb]}', 'Gitlab::Server', NULL, NULL ) was aborted: ERROR: relation "resource_events_20200103z" does not exist {{ Position: 13 Call getNextException to see other errors in the batch.}} Downgrading puppetdb from 6.8.0-1stretch to puppetdb 6.7.3-1stretch fixed this for us in the meanwhile. Environment:
Debian stretch
Postgres 9.6
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Nick Walker commented on FACT-1858 Re: Provide an option to disable legacy facts so they are not sent to the master from the agent Gheorghe Popescu I see. Should there be another ticket for finding those places in Puppet that use legacy fact names and updating them to use structured fact names? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.253867.1527713421000.30229.1579622160204%40Atlassian.JIRA.
Jira (PUP-10237) User resource with allowdupe executes usermod -o without -u {uid} argument
Title: Message Title
Mihai Buzgau updated an issue
Puppet / PUP-10237
User resource with allowdupe executes usermod -o without -u {uid} argument
Change By:
Mihai Buzgau
Sprint:
PR NW - Triage 2020-02-05
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342488.1579263095000.30218.1579621500204%40Atlassian.JIRA.
Jira (PUP-10237) User resource with allowdupe executes usermod -o without -u {uid} argument
Title: Message Title
Mihai Buzgau updated an issue
Puppet / PUP-10237
User resource with allowdupe executes usermod -o without -u {uid} argument
Change By:
Mihai Buzgau
Sprint:
PR - Triage
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342488.1579263095000.30215.1579621440165%40Atlassian.JIRA.
Jira (FACT-2299) Facter 2.x release
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2299 Facter 2.x release Change By: Mihai Buzgau Sprint: PR NW - Triage 2020-02-05 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342349.157919275.30210.1579621200300%40Atlassian.JIRA.
Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Gheorghe Popescu commented on FACT-1858 Re: Provide an option to disable legacy facts so they are not sent to the master from the agent Nick Walker yes, user will be required to to add "legacy" to the blocklist in facter.conf. Yes, legacy facts will not be set to master There are several places in puppet where legacy facts are used by direct querying using `Facter.value` eg: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/group/groupadd.rb#L11 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.253867.1527713421000.30185.1579620600227%40Atlassian.JIRA.
Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Nick Walker commented on FACT-1858 Re: Provide an option to disable legacy facts so they are not sent to the master from the agent Gheorghe Popescu to confirm my understanding of this change... The user will be required to add "legacy" to the blocklist in facter.conf. This will make it so that legacy facts are not sent to the master during catalog compilation and thus not stored in PuppetDB? I don't understand what is meant by "`Facter.value` will still return the fact value in order not to break puppet" Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.253867.1527713421000.30171.1579620240308%40Atlassian.JIRA.
Jira (PUP-9819) Puppet Failure on MacOS 10.15 'Catalina' Beta3
Title: Message Title Gabriel Nagy commented on PUP-9819 Re: Puppet Failure on MacOS 10.15 'Catalina' Beta3 This might be fixed by PUP-10241, but I"m not 100% sure since the error looks a bit different. I'm still poking around to see what else broke with the addition of Catalina. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316143.1562866804000.30120.1579617060351%40Atlassian.JIRA.
Jira (PUP-10246) Cannot set/change password of a user resource on macOS 10.15
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-10246 Cannot set/change password of a user resource on macOS 10.15 Change By: Gabriel Nagy Summary: Cannot set/change password of a user resource on macOS 10.15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342832.1579616899000.30115.1579617000267%40Atlassian.JIRA.
Jira (PUP-10246) Cannot set/change password on macOS 10.15
Title: Message Title
Gabriel Nagy updated an issue
Puppet / PUP-10246
Cannot set/change password on macOS 10.15
Change By:
Gabriel Nagy
It looks like direct access to binary plists under {{/var/db/dslocal/nodes/Default/}} has been blocked beginning with macOS 10.15 (even with Full Disk Access activated), so we can no longer overwrite that file to set/change the password on an macOS user.{code}Error: Unable to write the file /var/db/dslocal/nodes/Default/users/testuser.plist. #{code}There's still _a way_ to circumvent this and still be able to modify passwords. It involves the use of the {{dsimport}} command to indirectly manipulate the contents of the binary user plist.For this, we need to have the {{ShadowHashData}} (which we previously wrote to the plist) in binary format, then converted to base64.Here is some ancient {{dsimport}} documentation (Apple seems to have removed all mentions of this tool since, but it still works): http://web.archive.org/web/20090106120111/http://support.apple.com/kb/TA21305?viewlocale=en_USBasically the steps would be to:1. If the user exists, remove the existing ShadowHashData (with dscl delete) - {{dscl -plist . read /Users/testuser}} should show no {{ShadowHashData}}2. Import the file with the base64-converted hash using dsimport: {{dsimport /file/to/import /Local/Default M}} - {{dscl -plist . read /Users/testuser}} should show the new {{ShadowHashData}}The challenge that remains is to correctly build the ShadowHashData plist, convert it to binary and then to base64, then build the dsimport file.As per the documentation above, this is a file that changes the hashed password of an existing account:{code}0x0A 0x5C 0x3A 0x2C dsRecTypeStandard:Users 2 dsAttrTypeStandard:RecordName base64:dsAttrTypeNative:ShadowHashDatatestuser:{code}
Add Comment
Jira (PUP-10246) Cannot set/change password on macOS 10.15
Title: Message Title Gabriel Nagy created an issue Puppet / PUP-10246 Cannot set/change password on macOS 10.15 Issue Type: Bug Assignee: Unassigned Created: 2020/01/21 6:28 AM Priority: Normal Reporter: Gabriel Nagy It looks like direct access to binary plists under /var/db/dslocal/nodes/Default/ has been blocked beginning with macOS 10.15 (even with Full Disk Access activated), so we can no longer overwrite that file to set/change the password on an macOS user. Error: Unable to write the file /var/db/dslocal/nodes/Default/users/testuser.plist. # There's still a way to circumvent this and still be able to modify passwords. It involves the use of the dsimport command to indirectly manipulate the contents of the binary user plist. For this, we need to have the ShadowHashData (which we previously wrote to the plist) in binary format, then converted to base64. Here is some ancient dsimport documentation (Apple seems to have removed all mentions of this tool since, but it still works): http://web.archive.org/web/20090106120111/http://support.apple.com/kb/TA21305?viewlocale=en_US Basically the steps would be to: 1. If the user exists, remove the existing ShadowHashData (with dscl delete) dscl -plist . read /Users/testuser should show no ShadowHashData 2. Import the file with the base64-converted hash using dsimport: dsimport /file/to/import /Local/Default M dscl -plist . read /Users/testuser should show the new
Jira (PUP-10245) Update Public-facing Puppet docs to remove osx1013
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-10245 Update Public-facing Puppet docs to remove osx1013 Issue Type: Task Assignee: Unassigned Created: 2020/01/21 4:27 AM Priority: Normal Reporter: Mihai Buzgau Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (PUP-10244) Update Public-facing Puppet docs to remove osx1012
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-10244 Update Public-facing Puppet docs to remove osx1012 Issue Type: Task Assignee: Unassigned Created: 2020/01/21 4:23 AM Priority: Normal Reporter: Mihai Buzgau Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (PUP-10243) Update Public-facing Puppet docs to remove Fedora 29
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-10243 Update Public-facing Puppet docs to remove Fedora 29 Issue Type: Task Assignee: Unassigned Created: 2020/01/21 4:19 AM Priority: Normal Reporter: Mihai Buzgau Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (PUP-10242) Update Public-facing Puppet docs to remove Fedora 28
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-10242 Update Public-facing Puppet docs to remove Fedora 28 Issue Type: Task Assignee: Unassigned Created: 2020/01/21 4:16 AM Priority: Normal Reporter: Mihai Buzgau Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (FACT-2305) Implement ipaddress fact for aix
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2305 Implement ipaddress fact for aix Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342717.1579604397000.29909.1579606140175%40Atlassian.JIRA.
Jira (FACT-2303) Implement ipaddress fact for macos
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2303 Implement ipaddress fact for macos Change By: Bogdan Irimie Team: Night's Watch Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342715.1579604331000.29881.1579604520052%40Atlassian.JIRA.
Jira (FACT-2304) Implement ipaddress fact for solaris
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2304 Implement ipaddress fact for solaris Change By: Bogdan Irimie Team: Night's Watch Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342716.1579604352000.29880.1579604460043%40Atlassian.JIRA.
Jira (FACT-2304) Implement ipaddress fact for solaris
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2304 Implement ipaddress fact for solaris Issue Type: Task Assignee: Unassigned Created: 2020/01/21 2:59 AM Priority: Normal Reporter: Bogdan Irimie Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (FACT-2305) Implement ipaddress fact for aix
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2305 Implement ipaddress fact for aix Issue Type: Task Assignee: Unassigned Created: 2020/01/21 2:59 AM Priority: Normal Reporter: Bogdan Irimie Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (FACT-2303) Implement ipaddress fact for macos
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2303 Implement ipaddress fact for macos Issue Type: Task Assignee: Unassigned Created: 2020/01/21 2:58 AM Priority: Normal Reporter: Bogdan Irimie Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (FACT-2302) Implement ipaddress fact for linux
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2302 Implement ipaddress fact for linux Issue Type: Task Assignee: Unassigned Created: 2020/01/21 1:17 AM Priority: Normal Reporter: Bogdan Irimie Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
