Skip to content
This repository has been archived by the owner. It is now read-only.

Update to latest master version #1

Open
wants to merge 47 commits into
base: master
Choose a base branch
from

Conversation

bugoff
Copy link
Member

@bugoff bugoff commented Mar 27, 2020

Updates our branch to the latest version. @jeroenj how do i update the live branch? Just create a PR with the metadatata.rb version update?

rmoriz and others added 15 commits August 2, 2019 12:18
Marked fullchain as a deprecated_property_alias
Pebble v2.x has breaking changes that need some futher overhaul here,
but for now use the v1.0.1 version so tests can pass once more.

Also ensure that available packages are updated in Debian-based testing
platforms.
Need lazy evaluation when using attributes in resources
Upgrades acme-client version to 2.0.6 which supports faraday 1.0.0 which is required by chef
Update default.rb (Closes #120)
@bugoff bugoff requested a review from jeroenj March 27, 2020 17:36
@bugoff bugoff self-assigned this Mar 27, 2020
@jeroenj
Copy link
Member

jeroenj commented Mar 31, 2020

Why do you need this? If I recall correctly we needed this for ACME v2 support which is part of the stable 4.1.0 release.

Currently upstream master is the latest stable version (4.1.2) so there is no longer a need for this custom fork.

You can get rid of it and just upload 4.1.2 to your Chef server or reference it in the cookbooks that depend on it.

@bugoff
Copy link
Member Author

bugoff commented Mar 31, 2020

Chef testing fails because it can't install the acme-client gem. Didn't we pin all the mirrored cookbooks so we can't have any problems when somebody updates them and we don't support it?

@jeroenj
Copy link
Member

jeroenj commented Apr 1, 2020

There's a difference in pinning and forking cookbooks. We had to fork this one because the changes we needed weren't released in a stable release yet.

The cookbook should still be pinned. E.g. in xplose-nginx you'll need to update the cookbook dependency to cookbook 'acme', '4.1.2' and drop the reference to this repository. That way the stable release (which is pinned to 4.1.2) will be uploaded and used.

essjayhch and others added 10 commits October 1, 2020 12:56
 # Problem
 Currently, if a certificate has a large number of alt-names in it, and one (or more) of them fail, the entire certificate is rejected. Unfortunately, there is no diagnostics returned to point out what has failed, only that something has.
 This makes it difficult to debug the problem from the server admin point of view.

 # Fix
 Adjust the block that triggers the fail so that it includes some additional information about what the failure is, and include it in the output
Adds a bit more information to authz failure
Fix 'satus' typo in cert creation ruby_block
fixes #51

As the ability to install DNS challenges into the infrastructure depends
on the site, I implemented this in a way that allows cfookbook authores
to specify how to supply this to the infrastructure using custom ruby
blocks.

There must be two blocks given to the resource if you want to use DNS
validation:

`install_authz_block` and `remove_authz_block`

There is an example in the README explaining how to use this.
implement an interface to support DNS challenges
detjensrobert and others added 22 commits July 16, 2021 16:47
Signed-off-by: Robert Detjens <[email protected]>
Chef 17 compatibility and test modernization
location can be configured via chef attributes
Make private key file location configurable
v4.1.5 added this field, and it's important to note that if
`private_key_file` exists, the contents will take precedence over
`private_key`.
The upstream file resource supports using both String and Integer for
owner/group properties. There are some use cases where setting the UID/GID is
needed instead of the name (i.e. Docker volumes).

Signed-off-by: Lance Albertson <[email protected]>
Allow Integer for owner and group properties
…_authz.status

add processing as a valid authz status
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.