Product training

The Locked DENY Set

Show production.deploy staying denied after an approval is recorded.

Explanation

What you are learning

Recommended first: HIOP Fundamentals. You can still study this lesson.

Some effects are locked. production.deploy is one of them on this workstation. Marking the request approved does not change the outcome. Recording the approval as a fact does not change the next request either. Both measured decisions are DENY, reason locked deny, dispatch false, executed false. Do not deploy. Locked DENY stays DENY. Approval is not an override.

Worked example

Teaching workstation

These fields were returned by the teaching workstation for this lesson. They are not a production permit.

Locked effect, approval flag on the request

Ask for production.deploy with an approval flag

outcome
DENY
dispatch
false
executed
false
reason
locked_deny
effect
production.deploy
actor id
operator
resource
release
request id
lock-1

The approval fact is stored

Record the approval

dispatch
false
executed
false
request id
lock-1
mints authority
no
approval
recorded fact

A second request stays locked

Ask again with a new request id and the same flag

outcome
DENY
dispatch
false
executed
false
reason
locked_deny
effect
production.deploy
actor id
operator
resource
release
request id
lock-2
Exercise

Try it before you check

Read both deploy rows before you answer. The flag and the fact are already in the run.

What is the outcome of production.deploy after the approval is recorded?
Assessment

Explain the result

Can approval override DENY?

This lesson is not complete yet.

Materials

Use these with the lesson

Previous lessonCourse

A passed check is saved in this browser so you can resume. It is not a certificate, not an accreditation, and not authority to run an effect.