Best Practice for different regions

Welcome Forums DSC (Desired State Configuration) Best Practice for different regions

This topic contains 2 replies, has 3 voices, and was last updated by

1 year, 8 months ago.

  • Author
  • #73054

    Points: 3
    Rank: Member

    Does anyone have a suggestion on service ID's for different regions(DEV, QA, PROD). I have to run a service in each region with different service ID's.

    service foo {
    name = 'foo'
    credential = DEV|QA|PROD

    Currently I have utilizing a separate configuration data file, but I'm open to anything.

  • #74060

    Points: 1,811
    Helping HandTeam Member
    Rank: Community Hero

    Either configuration data file or a configuration database that you can build and query from. At some point, that database is probably going to be necessary for a lot of different tasks, so starting that build-out might be proactive.

  • #75355

    Points: 0
    Rank: Member

    You might also be able to address this using a Release Management solution. For example, I would approach this scenario in Visual Studio Team Services by setting those values as stored variables in the service, and then call them in each Environment for the Release definition.

    More information about this approach is documented here (but not specifically for DSC, and it assumes you are well versed in VSTS):

    There is a blog post series here as of April 2017, that introduces some of the concepts of how and why to use VSTS with DSC. I will reach out to the author and suggest a Release Management post would also be very helpful.

The topic ‘Best Practice for different regions’ is closed to new replies.

denizli escort samsun escort muğla escort ataşehir escort kuşadası escort