Context
Reploy currently creates reploy-staging/ when reploy stage is used without --dir. Now that generated deployment controllers use the intentionally generic appctl basename, a path such as:
contains no application identity. It is also easy for staging workspaces for different applications to collide in the same parent directory.
An environment-specific directory produces a clearer and self-describing control surface:
omegaconf-inspector-staging/appctl
Consider
Default staging directories to <environment.id>-staging after resolving the blueprint. Preserve explicit --dir as the override.
For example:
reploy stage omegaconf-inspector-demo
cd omegaconf-inspector-staging
reploy build
./appctl up
Workflow implications
The current constant reploy-staging lets commands such as reploy build find staging state from the parent directory without --dir. A dynamic default cannot provide that behavior without an additional discovery rule.
The implementation and documentation should choose an explicit model:
- prefer operating from inside the generated staging directory, where existing current-directory discovery works; or
- require
--dir <environment.id>-staging when operating from its parent.
Avoid silently selecting among multiple *-staging directories. If broader parent-directory discovery is introduced, it should succeed only when exactly one validated Reploy staging deployment is present and otherwise require --dir.
Reploy is not released yet, so backward compatibility with the reploy-staging default is not required.
Context
Reploy currently creates
reploy-staging/whenreploy stageis used without--dir. Now that generated deployment controllers use the intentionally genericappctlbasename, a path such as:contains no application identity. It is also easy for staging workspaces for different applications to collide in the same parent directory.
An environment-specific directory produces a clearer and self-describing control surface:
Consider
Default staging directories to
<environment.id>-stagingafter resolving the blueprint. Preserve explicit--diras the override.For example:
reploy stage omegaconf-inspector-demo cd omegaconf-inspector-staging reploy build ./appctl upWorkflow implications
The current constant
reploy-staginglets commands such asreploy buildfind staging state from the parent directory without--dir. A dynamic default cannot provide that behavior without an additional discovery rule.The implementation and documentation should choose an explicit model:
--dir <environment.id>-stagingwhen operating from its parent.Avoid silently selecting among multiple
*-stagingdirectories. If broader parent-directory discovery is introduced, it should succeed only when exactly one validated Reploy staging deployment is present and otherwise require--dir.Reploy is not released yet, so backward compatibility with the
reploy-stagingdefault is not required.