This message was deleted.

sparse-intern-71089

05/10/2021, 5:46 AM

This message was deleted.

✅ 1

miniature-advantage-31279

05/10/2021, 7:06 AM

I also think it is bit confusing, from my understanding

stack

is environment (dev, staging, prod). so the file main is not change (you are correct), you define it in the YAML as config or you can put if statement to check what stack you are on if you need to code something different

refined-activity-51649

05/11/2021, 12:22 AM

Thank you very much. I did like this:

Copy code

import pulumi

stack_name = pulumi.get_stack()

if stack_name == "dev":
    import main_dev
elif stack_name == "prod":
    import main_prod
elif stack_name == "test":
    import main_test

miniature-musician-31262

05/12/2021, 5:31 PM

That’ll work. It would be good to know a bit more about what those files contain, too. If they contain mostly configuration settings, another best practice is to use Pulumi’s config system, which lets you pull those values into a file that it reads automatically at runtime. https://www.pulumi.com/docs/intro/concepts/config/

miniature-musician-31262

05/12/2021, 5:31 PM

This lets you use the same code to drive all environments, using configuration settings to adjust what’s unique to each environment.

refined-activity-51649

05/13/2021, 12:57 AM

Wow. Thanks. For now each files only needs stack name of each, but later definitely I will use configuration.

👍 1

2 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.