How can I gain Redis permission to create a dynamic packet?

[GTI-Dakota]

Hello,

I hope you are all doing well! I am unable to generate a dynamic packet in the script runner. I have read the documentation on dynamic packets here. My plan is to generate a packet at the beginning of a suite/script so it can be offloaded later. However, my target_model = OpenC3::TargetModel.get_model(name: 'COSMOS_UTIL', scope: 'DEFAULT') line is erroring with PermissionError : NOPERM No permissions to access a key (redis://openc3-redis:6379). Is there anything I am missing?

My code is as follows:

require 'openc3'
require 'openc3/api/api'

include OpenC3::Api
$openc3_scope = "DEFAULT"

# Create a new packet
packet = OpenC3::Packet.new('COSMOS_UTIL', 'TEST_PACKET')
# Modify the packet by appending new items to it
packet.append_item('TEST_UINT', 32, :UINT)
packet.append_item('TEST_FLOAT', 32, :FLOAT)
packet.append_item('TEST_INT', 32, :INT)

# Grab the TargetModel associated with the packet's target
target_model = OpenC3::TargetModel.get_model(name: 'COSMOS_UTIL', scope: 'DEFAULT')
# Update the target model with the new packet
target_model.dynamic_update([packet])

Best,

Dakota

[jmthomas]

Per the docs, dynamic packets are meant to be created at installation time ... not runtime. Also if you're running in Script Runner you should not use API but use Script instead.

What are you trying to accomplish? We also have the Stash API for storing data between script runs.

[GTI-Dakota]

Per the docs, dynamic packets are meant to be created at installation time ... not runtime.

Gotcha. I wasn't concerned with microservice restarts so I assumed the API was fine to use during runtime. If that's not possible no worries at all. Thanks for the reminder of using "Script" instead. I had initially required that file with no luck either.

What are you trying to accomplish?

I'm looking to generate a new packet that is exclusive to the runtime of a script. I would like to effectively create a "checklist" packet that allows operator signoff of critical test steps with injected tlm so when a functional test is run so that when I extract packet data I will also have a "[timestamp]_FUNCTIONAL_SCRIPT_X_CHECKLIST" packet that is bundled with the rest of the target and packet data. The reason I'm looking to use dynamic packets is so that I can run the same script many times over without updating the "checklist" packet from a previous script execution. Based on this goal, I don't think the Stash API is what I'm looking for.

[ryanmelt]

I would recommend just creating a regular packet that is only received based on inject_tlm.