Skip to content

Add explanation for nodefault git ref deploy in dev #32

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.

Sign up for GitHub

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

Merged
edegenetais-nx merged 2 commits into from
Oct 14, 2024
Merged

Add explanation for nodefault git ref deploy in dev #32

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f8ae9c5
Explain how to test non default git references in dev.
Sep 10, 2024
fa1a075
Replacing directly by the instance name to make things clear.
Oct 14, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,15 @@

A suite of deployment scripts for the many components (message broker, DBs, prometheus, alertmanager, etc..) that make up the ProSanteConnect ecosystem

## Test in dev instances

To avoid confusion, waypoint projects should be left to point to their environement branch.
However, to test a specific version in the dev instance,
another reference may be deployed by adding `-remote-source=ref=<gitref>`
to the `waypoint up` command. For example, to test main in developement :

`waypoint up -local=false -remote-source=ref=main`

## Distribution history

This ecosystem uses many independant components, some of which live an independant life in distinct repositories.
Expand Down