The deployer can deploy the app but fail to publish DnsRecord and ApplicationDeploymentRecord #13
Labels
No Label
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cerc-io/webapp-deployment-status-api#13
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Basically, if the deployer is setup correctly, but the
laconic.yml
is misconfigured (and so doesn't publish records) we end up in a situation where an app has actually deployed, but isn't registered onchain.example: https://pwa-test-13-b311b1142a.pwa.kenz.world
this app has no DnsRecord or ApplicationDeploymentRecord, but the deployer deployed it.
This is expected deployer behaviour (AFIACT) but could confuse users
Tight consistency isn't possible here, but the deployer could do some sort of pre-flight check that its config is correct, I think -- try to publish a test record, something like that.
i think all that's needed here is for the deployer logs to surface
laconic
failures, or even just the logs normally viewed at the UI --> green deployed button --> black screen with logs, to be included in the deployer logssee cerc-io/laconicd#55 for a commonly encountered error: