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

support deploying on existing vpc on aws #1807

Merged
merged 6 commits into from
May 18, 2023
Merged

support deploying on existing vpc on aws #1807

merged 6 commits into from
May 18, 2023

Conversation

Adam-D-Lewis
Copy link
Member

@Adam-D-Lewis Adam-D-Lewis commented May 17, 2023

Reference Issues or PRs

What does this implement/fix?

Put a x in the boxes that apply

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds a feature)
  • Breaking change (fix or feature that would cause existing features not to work as expected)
  • Documentation Update
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no API changes)
  • Build related changes
  • Other (please describe):

Testing

  • Did you test the pull request locally?
  • Did you add new tests?

Any other comments?

@Adam-D-Lewis Adam-D-Lewis requested a review from costrouc May 17, 2023 14:09
**config.get("aws", {}).get("terraform_overrides", {}),
**config.get("amazon_web_services", {}).get("terraform_overrides", {}),
Copy link
Member Author

@Adam-D-Lewis Adam-D-Lewis May 17, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These terraform overrides were not usable before as far as I can tell. You'd get an error from pydantic that extra fields (the aws field) weren't allowed when I added an aws section to the nebari-config.yaml.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now they can be used via (e.g.)

amazon_web_services:
  terraform_overrides:
    existing_subnet_ids: ["subnet-05b2b1f41f0b1d8a6", "subnet-017efc3309fbca2da"]
    existing_security_group_id: "sg-0e2c865bdd8824b1a"
  region: ...
  <other_attributes>: ...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it worth formalizing these the available terraform_overrides in the schema?

@Adam-D-Lewis Adam-D-Lewis requested a review from iameskild May 17, 2023 23:45
@Adam-D-Lewis Adam-D-Lewis changed the title support deploying on existing vpc on aws [WIP] support deploying on existing vpc on aws May 17, 2023
Copy link
Member

@iameskild iameskild left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Adam-D-Lewis I had a few questions. This looks like a worthwhile addition :)

**config.get("aws", {}).get("terraform_overrides", {}),
**config.get("amazon_web_services", {}).get("terraform_overrides", {}),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it worth formalizing these the available terraform_overrides in the schema?

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

Successfully merging this pull request may close these issues.

2 participants