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

Stackpack: Gitea #29

Merged
merged 4 commits into from
Mar 4, 2024
Merged

Stackpack: Gitea #29

merged 4 commits into from
Mar 4, 2024

Conversation

gordon-klotho
Copy link
Contributor

@gordon-klotho gordon-klotho commented Mar 4, 2024

Requires klothoplatform/klotho#952

Also includes:

  • improvements to temp directory behaviour so that a single temp dir is used per request. This makes it easier to debug when using KEEP_TMP
  • Added regen query parameter to install to force regeneration, useful for testing

@gordon-klotho gordon-klotho changed the base branch from main to pulumi_assume_role March 4, 2024 16:27
Comment on lines +39 to +45
tmp_dir = TempDir()
if regen:
logger.info("Regenerating iac for %s", user_pack.id)
stack_packs = get_stack_packs()
_, iac = await user_pack.run_pack(stack_packs, store, tmp_dir.dir)
else:
iac = store.get_iac(user_pack.id)
Copy link
Contributor

Choose a reason for hiding this comment

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

just as a note, were always going to have to regenerate if the base stack hasnt been deployed since we wont know the imports yet, so this will likely change a little soon

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, makes sense. I just made this real quick since I kept forgetting to run the PATCH before install.

Comment on lines +121 to +123
# Make sure the SG rule is added to allow the LB in public subnets
# to talk to the ECS service in private subnets
aws:load_balancer:gitea-lb -> aws:ecs_service:gitea-service:
Copy link
Contributor

Choose a reason for hiding this comment

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

yeah this is an important note for all of them, we should still always have explicit edges between our major resources to ensure path solving runs

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Feels like this should be solvable from the engine to prevent such situations (took me a bit of investigation to figure out this was happening). In the meantime though, explicit edges will be required as you mentioned.

@gordon-klotho gordon-klotho changed the base branch from pulumi_assume_role to main March 4, 2024 17:04
@gordon-klotho gordon-klotho merged commit 7d4f9f1 into main Mar 4, 2024
2 checks passed
@gordon-klotho gordon-klotho deleted the gitea branch March 4, 2024 17:18
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.

2 participants