No valid config data found to send audit log event for deployment | Community
Skip to main content
B
BhavaniBharani
Level 4
December 17, 2024
Solved

No valid config data found to send audit log event for deployment

  • December 17, 2024
  • 1 reply
  • 755 views

Hi,

 

I am facing an issue in the app builder where, when i try to do aio app deploy i am getting this warning, No valid config data found to send audit log event for deployment. so i did the below 

1. aio app config set log-forwarding
? select log forwarding destination Adobe I/O Runtime
Log forwarding is set to 'adobe_io_runtime'
Log forwarding settings are saved to the local configuration
2. aio app config get log-forwarding

destination: adobe_io_runtime
settings: { updated_at: null }. Still i see

New Extension Point(s) in Workspace 'Stage': 'dx/asset-compute/worker/1'
Successful deployment 🏄.

But there is no runtime action is coming in the developer console runtime page.

 

Anyone is having idea, what could be the issue.

 

 

Thanks,

Bhavani Bharanidharan

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by TarunKumar

Hi @bhavanibharani ,

 

To add Adobe I/O Runtime Action to the project, you can initialize the project for local development. On local machine open terminal, navigate to where you want to initialize your project and follow these steps:

  • Initialize project by running

     

    aio app init

    Select the Organization, the Project you created in the previous step, and the workspace. In What templates do you want to search for? step, select All Templates option.

  • From the templates list, select @adobe/generator-app-excshell option.

  • Open project in your favorite IDE, for example VSCode.

  • The selected Extensibility template (@adobe/generator-app-excshell) provides a generic runtime action, the code is in src/dx-excshell-1/actions/generic/index.js file. Let’s update it to keep it simple, log the event details and return a success response. However in the next example, it is enhanced to process the received AEM Events.

    const fetch = require("node-fetch");
const { Core } = require("@adobe/aio-sdk");
const {
errorResponse,
getBearerToken,
stringParameters,
checkMissingRequestInputs,
} = require("../utils");

// main function that will be executed by Adobe I/O Runtime
async function main(params) {
// create a Logger
const logger = Core.Logger("main", { level: params.LOG_LEVEL || "info" });

try {
    // 'info' is the default level if not set
    logger.info("Calling the main action");

    // log parameters, only if params.LOG_LEVEL === 'debug'
    logger.debug(stringParameters(params));

    const response = {
    statusCode: 200,
    body: {
        message: "Received AEM Event, it will be processed in next example",
    },
    };

    // log the response status code
    logger.info(`${response.statusCode}: successful request`);
    return response;
} catch (error) {
    // log any server errors
    logger.error(error);
    // return with 500
    return errorResponse(500, "server error", logger);
}
}

exports.main = main;
     

  • Finally, deploy the updated action on Adobe I/O Runtime by running.

1 reply

TarunKumar
Community Advisor
TarunKumarCommunity AdvisorAccepted solution
Community Advisor
December 18, 2024

Hi @bhavanibharani ,

 

To add Adobe I/O Runtime Action to the project, you can initialize the project for local development. On local machine open terminal, navigate to where you want to initialize your project and follow these steps:

  • Initialize project by running

     

    aio app init

    Select the Organization, the Project you created in the previous step, and the workspace. In What templates do you want to search for? step, select All Templates option.

  • From the templates list, select @adobe/generator-app-excshell option.

  • Open project in your favorite IDE, for example VSCode.

  • The selected Extensibility template (@adobe/generator-app-excshell) provides a generic runtime action, the code is in src/dx-excshell-1/actions/generic/index.js file. Let’s update it to keep it simple, log the event details and return a success response. However in the next example, it is enhanced to process the received AEM Events.

    const fetch = require("node-fetch");
const { Core } = require("@adobe/aio-sdk");
const {
errorResponse,
getBearerToken,
stringParameters,
checkMissingRequestInputs,
} = require("../utils");

// main function that will be executed by Adobe I/O Runtime
async function main(params) {
// create a Logger
const logger = Core.Logger("main", { level: params.LOG_LEVEL || "info" });

try {
    // 'info' is the default level if not set
    logger.info("Calling the main action");

    // log parameters, only if params.LOG_LEVEL === 'debug'
    logger.debug(stringParameters(params));

    const response = {
    statusCode: 200,
    body: {
        message: "Received AEM Event, it will be processed in next example",
    },
    };

    // log the response status code
    logger.info(`${response.statusCode}: successful request`);
    return response;
} catch (error) {
    // log any server errors
    logger.error(error);
    // return with 500
    return errorResponse(500, "server error", logger);
}
}

exports.main = main;
     

  • Finally, deploy the updated action on Adobe I/O Runtime by running.

    Terms & ConditionsAccessibility statement

    Loading footer...