Skip to content
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

aws iotsitewise describe-portal --portal-id does not include edgeConfig/edgeAccess values within the AWS response. #9182

Open
1 task
bobneuman opened this issue Jan 2, 2025 · 0 comments
Assignees
Labels
bug This issue is a bug. investigating This issue is being investigated and/or work is in progress to resolve the issue. iotsitewise p2 This is a standard priority issue

Comments

@bobneuman
Copy link

Describe the bug

aws iotsitewise describe-portal --portal-id [idnumber] does not display the information related to the edgeConfig enablement that is returned within the response from AWS.
I you run the command with --debug the MainThread - botocore.parsers - DEBUG - Response body: {} includes the "edgeConfig": { "edgeAccess": "ENABLED" }, but the cli output does not.

Regression Issue

  • Select this option if this issue appears to be a regression.

Expected Behavior

I'd expect the cli to display the information in the MainThread - botocore.parsers - DEBUG - Response body: {}

Current Behavior

The cli of aws iotsitewise describe-portal --portal-id _____ fails to include the "edgeConfig": { "edgeAccess": "ENABLED" } or "edgeConfig": null

Reproduction Steps

Create a sitewise edge portal and use the id to query aws iotsitewise describe-portal --portal-id _____ --debug. A review of the MainThread - botocore.parsers - DEBUG - Response body should have "edgeConfig": null. Then using the console navigate to the portal and enable the edge (see. ___ ). Wait a few minutes and rerun the command aws iotsitewise describe-portal --portal-id _____ --debug the debug content will include "edgeConfig": { "edgeAccess": "ENABLED"} , but the cli output will not.

Possible Solution

No response

Additional Information/Context

Update the Create and Update Portal functions of the cli to allow setting the edgeAccess to ENABLED. Cloudtrail captures the following when the setting is altered in the console.

  { .....
    "eventName": "UpdatePortal",
    ....
    "requestParameters": {
        "portalName": "My-Portal",
        "roleArn": "arn:aws:iam::123456789011:role/AWSIoTSiteWiseMonitorServiceRole",
        "clientToken": "aaaaaaaa-bbbb-cccc-ddddddddddd",
        "portalId": "aaaaaaaa-bbbb-cccc-ddddddddddd",
        "portalContactEmail": "[email protected]",
        "edgeConfig": {
            "edgeAccess": "ENABLED"
        },
        "portalDescription": "My-Portal description"
    },

CLI version used

aws-cli/2.22.26 Python/3.12.6

Environment details (OS name and version, etc.)

Linux/6.1.0-27-amd64 exe/x86_64.debian.12

@bobneuman bobneuman added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Jan 2, 2025
@RyanFitzSimmonsAK RyanFitzSimmonsAK self-assigned this Jan 2, 2025
@RyanFitzSimmonsAK RyanFitzSimmonsAK added investigating This issue is being investigated and/or work is in progress to resolve the issue. p2 This is a standard priority issue iotsitewise and removed needs-triage This issue or PR still needs to be triaged. labels Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. investigating This issue is being investigated and/or work is in progress to resolve the issue. iotsitewise p2 This is a standard priority issue
Projects
None yet
Development

No branches or pull requests

2 participants