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

ttlSchedule: Schedule can't be edited via UI if timestamp does not end in :00Z #452

Closed
MitchellGerdisch opened this issue Dec 3, 2024 · 0 comments
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Milestone

Comments

@MitchellGerdisch
Copy link

What happened?

The ttlSchedule resource takes a timestamp of the form 2020-01-01T00:00:00Z as per https://www.pulumi.com/registry/packages/pulumiservice/api-docs/ttlschedule/#timestamp_nodejs

If the timestamp that is provided does NOT end in :00Z but instead is set to, say, :23Z then if you try to edit the schedule in the UI, it will not update (nor throw an error).

Example

Add the following code or similar to a stack that has a deployment set up:

ttlsched = pulumiservice.TtlSchedule(f"{config.base_name}-ttlsched", pulumiservice.TtlScheduleArgs(
    organization=pulumi.get_organization(),
    project=pulumi.get_project(),
    stack=pulumi.get_stack(),
    timestamp="2025-12-04T03:38:22Z",
    # timestamp="2025-12-05T13:23:00Z"
))
  • Run the stack
  • Go to the UI and try to edit the TTL schedule time and hit Save Schedule.
  • Nothing will happen.
  • And when you cancel out you'll see the schedule hasn't been updated.
  • Looking at Developer Tools output, you'll see an error like:
    • "message": "Bad Request: decoding JSON: parsing time \"2025-12-04T05:38:10:00Z\" as \"2006-01-02T15:04:05Z07:00\": cannot parse \":00Z\" as \"Z07:00\""
  • update the code to use the timestamp that ends in :00Z and run the stack and try to update the schedule via the UI and it'll work fine.

Either the pulumi service provider should error if indeed it shouldn't be accepting timestamps that end in something other than :00Z or it should just overwrite the time to have :00Z at the end since it's not applicable in the UI anyway.

Output of pulumi about

CLI
Version 3.139.0
Go Version go1.23.3
Go Compiler gc

Plugins
KIND NAME VERSION
resource aws 6.62.2
resource command 0.11.1
resource pulumiservice 0.27.1
language python unknown
resource stackmgmt 3.3.4

Host
OS darwin
Version 15.1
Arch x86_64

This project is written in python: executable='/Users/mitch/Downloads/stack-mgmt-autobuild/elegant-ytterbium-kakapo/venv/bin/python' version='3.11.8'

Backend
Name pulumi.com

Dependencies:
NAME VERSION
netaddr 1.3.0
pequod_stackmgmt 3.3.4
pip 24.0
pulumi_aws 6.62.2
setuptools 65.5.0

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@MitchellGerdisch MitchellGerdisch added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Dec 3, 2024
@komalali komalali removed the needs-triage Needs attention from the triage team label Dec 4, 2024
@komalali komalali added this to the 0.115 milestone Dec 4, 2024
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Development

No branches or pull requests

4 participants