Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

2 Resource Credentials with the same name but assign to 2 environnements or more not working



  • Hello

    I am looking to use the same account for some plan but its password is not the same depending on the environment it is applied.
    It can use in the plan $CredentialProperty() and get a different password depending on the environnement it is apply.

    Ressource Credential:

    ADACCOUNT => login:ADAccount / pwd:simplepassaword assign to TEST environnement
    ADACCOUNT => login:ADAccount / pwd:verycomplexpassword assign to PROD environnement
    

    Unfortunately, there is a constraint violation

    System.Data.SqlClient.SqlException (0x80131904): 2627`14`1`Credentials_CreateOrUpdateCredential`21`Violation de la contrainte UNIQUE KEY « UQ__Credentials ». blablabla
    

    It is a bug ?
    If not, it would be a very useful feature

    Adding the ability to assign the credentail to multiple environment would be better:).
    (One to TEST, DEV, INTEGRATION and the second one to (PROD and PRA) for example.

    Best regards

    Philippe

    Product: BuildMaster
    Version: 6.1.0


  • inedo-engineer

    Hi Philippe,

    I know it's been a while since this question was posted, but just wanted to let you know that we will soon be supporting the behavior in Otter of allowing multiple resource credentials of the same name that differ only by environment.

    We are still in the process of determining the UI (e.g. allowing selection of multiple environments at once) but at least the core functionality you described will work.

    This is being targeted for Otter v2.2.5 due out July 26.

    Hope this helps,
    -John



  • Hi John
    Thanks for this reply.
    I needed such feature for Buildmaster😂, but in Otter it is good too 😀


  • inedo-engineer

    Aha, it will also be included in BuildMaster... not sure why I got stuck on Otter. I guess it was on my mind because we just had a maintenance release today :)

    This feature is also scheduled for BuildMaster v6.1.10 on July 19


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation