[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fYsBgu1bR7AY8dypurUBVb4ihI_8fC--l5Bfm8GUPkVQ":3,"$frLLMnwpA97bWocRqGBZk8m2mO6b2DL6Z-YoX6_gxttk":9},{"data":4},{"name":5,"slug":6,"description":7,"meta_title":8,"meta_description":7},"امنیت و DevSecOps","security","امن‌سازی زیرساخت و پایپلاین، مدیریت دسترسی و اسرار، و جا دادن امنیت در چرخه تحویل نرم‌افزار.",null,{"data":10,"links":32,"meta":34,"featured":8},[11],{"id":12,"title":13,"slug":14,"excerpt":15,"cover":16,"category":18,"author":19,"track":23,"level":26,"reading_minutes":29,"is_featured":30,"published_at":31,"updated_at":31},10,"رفع خطای 429 در Trivy DB با راه‌اندازی mirror داخلی","trivy-db-429-rate-limit-mirror","اگر مرحله اسکن Trivy در پایپلاین با خطای 429 Too Many Requests شکست می‌خورد، مشکل از کد یا شبکه شما نیست؛ GHCR نرخ pull ناشناس را محدود می‌کند. در این مقاله پایگاه‌داده Trivy را در رجیستری داخلی mirror می‌کنیم و Trivy را به آن وصل می‌کنیم.",{"url":17,"alt":13},"https:\u002F\u002Fapi.cloudicap.com\u002Fmedia\u002Fposts\u002Fcd38c70f-05ae-4f49-aa18-24ae7740ace1.webp",{"name":5,"slug":6},{"name":20,"slug":21,"role":22,"avatar_url":8},"تحریریه کلودیکپ","cloudicap-editorial","تیم محتوای کلودیکپ",{"value":24,"label":25},"engineers","مهندسان",{"value":27,"label":28},"intermediate","متوسط",8,false,"2026-10-11T08:54:50+00:00",{"first":33,"last":33,"prev":8,"next":8},"https:\u002F\u002Fapi.cloudicap.com\u002Fapi\u002Fv1\u002Fblog\u002Fposts?page=1",{"current_page":35,"from":35,"last_page":35,"links":36,"path":44,"per_page":45,"to":35,"total":35},1,[37,39,42],{"url":8,"label":38,"page":8,"active":30},"« Previous",{"url":33,"label":40,"page":35,"active":41},"1",true,{"url":8,"label":43,"page":8,"active":30},"Next »","https:\u002F\u002Fapi.cloudicap.com\u002Fapi\u002Fv1\u002Fblog\u002Fposts",9]