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

Allow deployment slot settings #839

Closed
wants to merge 65 commits into from
Closed

Allow deployment slot settings #839

wants to merge 65 commits into from

Conversation

nargiz
Copy link
Contributor

@nargiz nargiz commented Dec 6, 2021

This PR closes #838

The changes in this PR are as follows:

  • Allows you to specify slot settings for web app/functions using slot_setting and slot_settings

I have read the contributing guidelines and have completed the following:

  • Tested my code end-to-end against a live Azure subscription.
  • Updated the documentation in the docs folder for the affected changes.
  • Written unit tests against the modified code that I have made.
  • Updated the release notes with a new entry for this PR.
  • Checked the coding standards outlined in the contributions guide and ensured my code adheres to them.

If I haven't completed any of the tasks above, I include the reasons why here:

r30e and others added 30 commits June 8, 2021 08:41
Improve support for slots, including copying appsettings and adding m…
Made slot copy all site settings and overwrite/merge those it cares about
fixed tests depending on order of generated resources
The only config option is the path, the "time before unhealthy instances are removed" option isn't configurable via ARM.
- refactored match this.CustomDomain statement
- edited releasenotes
- edited docs ... resources/web-app.md
- eval at arm level, used for the resourceGroup property
- builders resourcegroup/app changed to acocomodate ArmExpression name type change
- NoDomain changed
…t stays coated with extra quote marks

- amended test to reflect that
r30e and others added 28 commits August 31, 2021 11:43
Revert "Custom domains for Web App"
Slots should not have a Zip Deploy as a PostDeployTask
- Web.fs :  Added Certificate, HostnameBinding and SSlState types
- Builders.WebApp.fs : Builder now consideres CustomDomain property (SecureDomain, InsecureDomain, NoDomain)
- Types.fs : DomainConfig and CertificateOptions created as part of the CustomDomain property use in the WebApp builder

##Minor Changes
- resourceGroup.fs : Minor change to accomodate "[resourceGroup().name]" name in WebApp builder

##Comments/Concerns
- On testing the creation of an app managed certificate, I noticed that the thumbprint of the certificate createddoesn't show in the UI and the resource itself (when accessing resources.azure.com), I then saw [this article](https://docs.microsoft.com/en-us/azure/app-service/configure-ssl-certificate#:~:text=Does%20not%20support%20usage%20as%20a%20client%20certificate%20by%20certificate%20thumbprint%20(removal%20of%20certificate%20thumbprint%20is%20planned).)  which probably explains why. All tests ran fine.
update cert dependancy to not need service plan Id
Merge from compositionalIT/farmer
@nargiz nargiz closed this Dec 9, 2021
@nargiz
Copy link
Contributor Author

nargiz commented Dec 9, 2021

there was some mess with the branch when I tried to merge the changes to my organization. I will re-open a new one later

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

Successfully merging this pull request may close these issues.

Support deployment slot settings
6 participants