Help needed with clone private GitLab repo with contracts #900
-
Hi, I have a As its an option documented here https://specmatic.in/documentation/specmatic_json.html#source-control-authentication
I would like to avoid the token be pushed to the git in this config file. Is it possible to use environment variable in the repository url and specmatic resolve it from the CI scope? Or is there other ways to pass this token? PS: Unfortunately the token can be also be found in the Update Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
Any recommendations from the Specmatic team, how to get this done properly on GitLab? |
Beta Was this translation helpful? Give feedback.
-
Configuring Deploy keys worked on GitLab. |
Beta Was this translation helpful? Give feedback.
-
@tkrisztian95 Specmatic now substitutes env variables that are part of the Git repo URL that you mention in specmatic.json. This is part of the latest release 1.3.18. Here is the link to the documentation. With this you should be able to use Gitlab env variables as part of the Repo URI. Examples:
Adding this in this thread in addition to your deploy keys based solution for anyone referring to this discussion. |
Beta Was this translation helpful? Give feedback.
Configuring Deploy keys worked on GitLab.