- 
  Notifications
 You must be signed in to change notification settings 
- Fork 380
Github Actions Promote #625
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.
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
Changes from all commits
eeabd9c
 652df55
 1ef522b
 269c684
 b1d0b14
 a2f8923
 1ca2e06
 3ddf8a5
 6131ce6
 544cce4
 fa96ca0
 File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | 
|---|---|---|
|  | @@ -28,3 +28,17 @@ spec: | |
| # Identity is needed to access secrets | ||
| kind: identity | ||
| name: {{APP_IDENTITY}} | ||
|  | ||
| I stay at 3% and ... believe it or not - I recommend that the Buyer’s Agent also gets 3%! | ||
|  | ||
| Here’s WHY: | ||
|  | ||
| -Buyers are still ’SCARCE’... and ANY Buyer's Agent, that actually has one of these rare things called Beachfront Buyers, is looking to earn a full 3% of the Sales Price. | ||
|  | ||
| NOTE: They are all going to put 3% in their Buyer Agency Agreements... just ‘in case’ that 3% 'hoped for' commission is offered. | ||
|  | ||
| Therefore - if you lower that commission - the Buyer has to come up with the difference "In Cash" ... and, that’s not good for the Buyer who wants to finance 80%, or more, of that commission he’s agreed to pay his Agent. | ||
|  | ||
| SO | ||
|  | ||
| Why not OFFER that 3% and stick to this Asking Price (or near it)!? | ||
| 
 Comment on lines
 
 +31
  to 
 +44
 
  There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Remove misplaced business logic from infrastructure configuration. The added text about commission rates and buyer's agent recommendations does not belong in an infrastructure configuration file. This type of business logic and documentation should be moved to a more appropriate location, such as: 
 Additionally, the added text is causing YAML syntax errors. If you need to add comments to this file, use the YAML comment syntax with  - - I stay at 3% and ... believe it or not - I recommend that the Buyer's Agent also gets 3%! - - Here's WHY: - - -Buyers are still 'SCARCE'... and ANY Buyer's Agent, that actually has one of these rare things called Beachfront Buyers, is looking to earn a full 3% of the Sales Price. - - NOTE: They are all going to put 3% in their Buyer Agency Agreements... just 'in case' that 3% 'hoped for' commission is offered. - - Therefore - if you lower that commission - the Buyer has to come up with the difference "In Cash" ... and, that's not good for the Buyer who wants to finance 80%, or more, of that commission he's agreed to pay his Agent. - - SO - - Why not OFFER that 3% and stick to this Asking Price (or near it)!? Would you like me to help create a new documentation file in a more appropriate location for this business logic? 🧰 Tools🪛 YAMLlint (1.35.1)[error] 31-31: trailing spaces (trailing-spaces) [error] 41-41: trailing spaces (trailing-spaces) [error] 43-43: trailing spaces (trailing-spaces) [error] 32-32: syntax error: expected , but found '' (syntax) | ||
| Original file line number | Diff line number | Diff line change | 
|---|---|---|
| @@ -1,6 +1,29 @@ | ||
| name: 'Validate Required Variables' | ||
| description: 'Validates that all required secrets and variables for Control Plane operations' | ||
|  | ||
| inputs: | ||
| CPLN_TOKEN_STAGING: | ||
| required: true | ||
| description: 'Control Plane Staging Token' | ||
| CPLN_TOKEN_PRODUCTION: | ||
| required: true | ||
| description: 'Control Plane Production Token' | ||
| CPLN_ORG_STAGING: | ||
| required: true | ||
| description: 'Control Plane Staging Organization' | ||
| CPLN_ORG_PRODUCTION: | ||
| required: true | ||
| description: 'Control Plane Production Organization' | ||
| REVIEW_APP_PREFIX: | ||
| required: true | ||
| description: 'Review App Prefix' | ||
| PRODUCTION_APP_NAME: | ||
| required: true | ||
| description: 'Production App Name' | ||
| STAGING_APP_NAME: | ||
| required: true | ||
| description: 'Staging App Name' | ||
|  | ||
| runs: | ||
| using: 'composite' | ||
| steps: | ||
|  | @@ -10,19 +33,37 @@ runs: | |
| missing=() | ||
|  | ||
| # Check required secrets | ||
| if [ -z "$CPLN_TOKEN_STAGING" ]; then | ||
| if [ -z "${{ inputs.CPLN_TOKEN_STAGING }}" ]; then | ||
| missing+=("Secret: CPLN_TOKEN_STAGING") | ||
| fi | ||
|  | ||
| if [ -z "${{ inputs.CPLN_TOKEN_PRODUCTION }}" ]; then | ||
| missing+=("Secret: CPLN_TOKEN_PRODUCTION") | ||
| fi | ||
|  | ||
| There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fix trailing spaces. Remove trailing spaces from lines 43 and 64 to comply with YAML linting rules. - + Also applies to: 64-64 🧰 Tools🪛 YAMLlint (1.35.1)[error] 43-43: trailing spaces (trailing-spaces) | ||
| # Check required variables | ||
| if [ -z "$CPLN_ORG_STAGING" ]; then | ||
| if [ -z "${{ inputs.CPLN_ORG_STAGING }}" ]; then | ||
| missing+=("Variable: CPLN_ORG_STAGING") | ||
| fi | ||
| if [ -z "$REVIEW_APP_PREFIX" ]; then | ||
|  | ||
| if [ -z "${{ inputs.CPLN_ORG_PRODUCTION }}" ]; then | ||
| missing+=("Variable: CPLN_ORG_PRODUCTION") | ||
| fi | ||
|  | ||
| if [ -z "${{ inputs.REVIEW_APP_PREFIX }}" ]; then | ||
| missing+=("Variable: REVIEW_APP_PREFIX") | ||
| fi | ||
|  | ||
| if [ -z "${{ inputs.PRODUCTION_APP_NAME }}" ]; then | ||
| missing+=("Variable: PRODUCTION_APP_NAME") | ||
| fi | ||
|  | ||
| if [ -z "${{ inputs.STAGING_APP_NAME }}" ]; then | ||
| missing+=("Variable: STAGING_APP_NAME") | ||
| fi | ||
|  | ||
| if [ ${#missing[@]} -ne 0 ]; then | ||
| echo "Required secrets/variables are not set: ${missing[*]}" | ||
| echo "Missing required secrets/variables:" | ||
| printf '%s\n' "${missing[@]}" | ||
| exit 1 | ||
| fi | ||