Skip to content

Feature/stack configuration#147

Merged
isivaselvan merged 5 commits into
next-1.0.0from
feature/stack-configuration
May 12, 2026
Merged

Feature/stack configuration#147
isivaselvan merged 5 commits into
next-1.0.0from
feature/stack-configuration

Conversation

@isivaselvan

@isivaselvan isivaselvan commented May 8, 2026

Copy link
Copy Markdown
Collaborator

Description

Testing plan

External links

JIRA

Output from tests

Including output from tests may require access to a TFE instance. Ignore this section if you have no environment to test against.

> python examples/stack_configuration.py --stack-id st-2T46TUuZkA1

================================================================================
Listing stack configurations for stack: st-2T46TUuZkA1
================================================================================
- ID: stc-FcmozZLa
  Status: StackConfigurationStatus.FAILED
  Sequence: 1
  Speculative: False
  Created: 2026-05-07 11:32:17.031000+00:00
  Updated: 2026-05-07 11:32:50.500000+00:00

Total: 1 stack configurations

> python examples/stack_configuration.py --stack-id st-2T46TBE2ErUuZkA1 --read --id stc-FcmzxaTJ

================================================================================
Reading stack configuration: stc-FcmzxaTJeKBozZLa
================================================================================
ID: stc-FcmzxaTJeKBozZLa
Status: failed
Sequence: 1
Speculative: False
Created: 2026-05-07 11:32:17.031000+00:00
Updated: 2026-05-07 11:32:50.500000+00:00

> python examples/stack_configuration.py --stack-id st-2T46TBEA1 --create --speculative

================================================================================
Creating a new stack configuration
================================================================================
Created stack configuration: stc-yDAnQif
  Status: pending
  Speculative: True
  Sequence: None
  Created: 2026-05-08 07:28:07.027000+00:00



Rollback Plan

Changes to Security Controls

PCI review checklist

  • I have documented a clear reason for, and description of, the change I am making.

  • If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.

  • If applicable, I've documented the impact of any changes to security controls.

    Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

If you have any questions, please contact your direct supervisor, GRC (#team-grc), or the PCI working group (#proj-pci-reboot). You can also find more information at PCI Compliance.

@isivaselvan isivaselvan requested a review from a team as a code owner May 8, 2026 07:21
@isivaselvan isivaselvan merged commit fac1e9d into next-1.0.0 May 12, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant