Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot renew when using Testing-In-Production and running from a slot #394

Open
jvtroyen opened this issue Jul 28, 2021 · 0 comments
Open

Comments

@jvtroyen
Copy link

Extension used: 1.0.6.

We are using Testing-In-production as follows:

  • we have 2 slots: "staging" and "live"
  • we are not using the Production slot
  • we usually serve from the "live" slot (except during deploys)
  • we need to run the extension on Production because that's where domain names are defined and certificates should be installed
  • when running the extension, it does not find the generated acme challenge file because the file is generated on Production slot, but online verification happens against the "live" slot, which does not contain the file

I took the liberty of making a PullRequest:

  • added an extra input-field to the extension, where you enter the name of the TIP-slot (testing-in-production)
  • when storing the acme challenge file on Kudu, it takes this new property into account, making sure the file ends up somewhere that it can be found

Thanks for making this extension. I hope you deem this addition worthwhile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant