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

Introduce lifecycle configuration to allow proper resource recreation #14

Merged

Commits on Nov 8, 2017

  1. Introduce intermediary stage to allow proper resource recreation

    Unfortunately the current setup still has the issue that prevents us from replacing the API-GW resources when the Swagger file changes.
    
    Fortunately someone else has chimed in with their solution, and this seemed to work during my tests:
    hashicorp/terraform#6613 (comment)
    
    Also changed the output of the module to reflect custom domains.
    
    (My test case was only about changing the description variable of the API Gateway module, which affects the Swagger file.)
    szilveszter committed Nov 8, 2017
    Configuration menu
    Copy the full SHA
    bdb642e View commit details
    Browse the repository at this point in the history

Commits on Nov 9, 2017

  1. Some lifecycle configuration helps with the problem

    Let's use this instead of the intermediate step, seems much cleaner.
    szilveszter committed Nov 9, 2017
    Configuration menu
    Copy the full SHA
    6637c65 View commit details
    Browse the repository at this point in the history